|
"I have many colleagues who think the purpose of research is to please themselves." — Dave Parnas |
|
Last update 4-March, 2019 |
| Week | Date | Topic | Readings(R)/Papers(P)/Activities(A)/Resources | Lectures | Project |
|---|---|---|---|---|---|
| Part 1: Requirements Engineering Overview | |||||
| 1 | 7-January | Classes start January 9th, so no class. Be safe, have fun. | |||
| 2 | 14-January | Introduction, Overview of Software Engineering, Requirements Engineering | R: SWEBOK Ch. 1, Software Requirements book Ch. 1, 2 (Wiegers, Beatty); P: paper i, paper ii; A: class activity (not eligible for hands on activity report) | Requirements engineering basics, see Canvas for video lectures part 1 and part 2 under Files | Part 1 paper summary(ies) due today (if summarizing any of these papers - i and ii) |
| 3 | 21-January | Martin Luther King, Jr. Holiday at UK—no class. Be safe, have fun. | |||
| 4 | 28-January | Overview of Requirements Engineering | R: Software Requirements book Ch. 3, 14; P: paper iii, paper iv; A: class activity (not eligible for hands on activity report) | Writing better requirements - see Canvas for video lecture under Files, Specification - see Canvas for video lecture under Files, Non-functional requirements - see Canvas for video lecture under Files(NFR) | Part 1 paper summary(ies) due today (if summarizing any of these papers - iii and iv); Bids on papers due at start of class (from Part 2 of class -- as reviewer, dissenter) |
| Part 2: Requirements Engineering Activities/Methods/Techniques, Hands-on activities | |||||
| 5 | 4-February | Elicitation | R: Software Requirements book Ch. 7, 8; P: 8, 9; A: Requirements Elicitation: Functional and Non-Functional requirements (work on questions for elicitation first, then work with partner) and write handson activity report; Resources: | Inception, Elicitation, Prioritization | |
| 6 | 11-February | Elicitation - continued | R: Software Requirements book Ch. 16; P: 10, 11, 12; A: Creativity exercise to improve requirements elicitation, the assignment is here; Resources: | Management - see Canvas for video lecture under Files, Processes - see Canvas for video lecture under Files | |
| 7 | 18-February | Modeling and Formalism | R: Software Requirements book Ch. 12; P: 1, 2, 3; A: installOpenOME and look at this paper and read more on goal modeling and develop your own goal model for your project or a project of your choosing using OpenOME and run analysis on it and write a handson activity report; OR you can look at this assignment, activity #3 -- you can develop the UML class diagram, activity diagram (already provided), or sequence diagram (download ArgoUML or jucmnav or similar in order to draw it), use analysis feature in the tool, and write a handson report; Resources: | URN and GRL - see Canvas for video lecture under Files, UML2 - see Canvas for video lecture under Files | Project proposal posted by 20 February; PhD students turn in proposed topic of mini-lecture by 18 February class start |
| 8 | 25-February | Analysis & Projects | R: ; P: 6, 7, 7B, 7C; A: Requirements Analysis (with or without tool support), then write handson activity report; Resources: a reqt spec, another reqt spec | Requirements Verification and Validation - see Canvas for video lecture under Files | Paper summary/critique or hands on activity report #1 posted by start of class, and mandatory discussion week |
| 9 | 4-March (4-March midterm of Spr'19) | Safety Analysis & SPLs & Projects | R: ; P:, 13, 14; A: a) install Eclipse or STS and use New... Other.. and choose feature diagram..... and develop your own feature model and anayze it and write a handson activity report; or b) use SPLOT to build the model and analyze it and write handson report. Here is a short paper on SPLOT | Software Product Lines - please read, Safety Analysis - please read | Project plan posted by 4 March (optional); assignments made for project report reviews to MS and PhD students; PhD students turn in detailed outline of mini-lecture by 4 March class start |
| 10 | 11-March | Spring Break at UK—no class. Be safe, have fun. | |||
| 11 | 18-March | Security & Projects | R: ; P: 4, 5; A: Use Case Modeling (with or without tool support) - develop misuse cases for a project of your choice and write handson activity report; Resources: Are indicated and linked in the Use case modeling activity; CAIRIS for security and usability analysis - use the Acme water system or Neurogrid system examples in the demo and examine the various models and artifacts provided (requirements, personas, threats, risks) - how might you use this tool to assist with your security requirements work? Develop a few usage scenarios (for you as a user of CAIRIS). Add models or other artifacts to one of the system models. Add inconsistencies, then perform some validation on one of the systems using the tool. Generate documentation for one of the systems. Write handson activity report; Resources: many are available at the CAIRIS site including a user's manual. See files I added to Canvas with CAIRIS in the name - including our RE Cares 2018 Emergency Management case study (and IEEE Software paper explaining it). Contact me for more information. Please collect feedback for Prof. Faily if you use CAIRIS - he asks "I hope these resources are useful. If you do use any of the above resources, I would be interested in hearing what your experiences were." | Safety lecture - please read, also see Canvas file with the name Security*.txt | |
| 12 | 25-March | NLP, Legal | R: ; P: 15, 16, 17, 17B; A: Look at paper 17B and develop your own program to search a requirements document and identify lines of the document containing vague or ambiguous terms. Resources: Here are links that might help search text file in Java and search in C . There are requirements specifications to be searched under the 25 February handson activities on the schedule. Also, here under Resources, Community datasets, you can find requirements that have been parsed and placed one per file (you will have to read the dataset description to see which ones, some will be .xml, some .txt). | Writing hints
(A, B, C, D) | Paper summary/critique or hands on activity report #2 posted by start of class, and mandatory discussion week; Hand out sample project reports | 13 | 1-April | Project Week | PhD lectures | Hand out sample presentations |
| 14 | 8-April | Traceability & Ethics | R: ; P: 18, 19, 20, 21, 22; A: Traceability: 1) RETRO.NET exercise and materials and write a handson activity report; 2) install TraceLab and follow this to build a component in Netbeans -- the students in my lab right now prefer VS and C# though, so consider this installation and Hello World instructions instead.....and write a handson activity report/ Ethics: pick one of the three ethics exercises listed here, and write handson report; in case SEERI link not working, read some of these items such as whistle blowers article (first one) and analyze and write handson report | Presentation hints
(A, B, C) | |
| Part 3: Student Project Presentations and Mini Hackathon | |||||
| 15 | 15-April | Mini hackathon UK | ****Draft reports due - 17 April at 3 pm.....Complete your reports. | Paper summary/critique or hands on activity report #3 posted by start of class, and mandatory discussion week | |
| 16 | 22-April | Presentations at UK | Project report reviews (MS and PhD) due 22-April start of class | ||
| Finals week | 30-April (Tuesday) 1530-1730 | Presentations at UK, if time slot needed final exam week | Final reports due Monday, April 29 | ||
| Top |